Journey Context
A form driven flow can be used in different digital journeys to collect data or trigger actions. Each form driven flow has an entity attached to it. In order to track the records inserted into the entity attached to a form driven flow, which in turn is used in two or more digital journeys, there is the journey context information. Such a context can be set to the whole form or just a step. To check the Journey Context of an entity, get its metadata and there will be displayed the journey context. Hence, it is easy to understand from which situation the records came.
The context must be named exactly as the digital journey's name in oder for it to work.
To set the context, access the desired form driven flow, and in the Advanced tab, in AfterEvents, add the following function setJourneyContext with the context set, i.e. the exact name of the digital journey. For example, a form driven flow called Gamma insurance is part of two digital journeys, one called LoanOrigination and another one called SMELoanOrigination. To set the context, insert the code:
ebs.setJourneyContext("LoanOrigination");
To see the context of the active session, use the function getJourneyContext, which will render the context of the session active at the time of the user calls it.
The context is related to the navigation flow as well when evaluating a rule for a particular digital journey. For details, see Flow Control.